System, method, and computer program product for identifying unwanted data communicated via a session initiation protocol

ABSTRACT

A system, method, and computer program product are provided for identifying unwanted data communicated via a session initiation protocol. In use, packets associated with an electronic message communicated over a network utilizing a session initiation protocol are identified. Additionally, it is determined whether the packets include unwanted data. Furthermore, a reaction is performed, based on the determination.

FIELD OF THE INVENTION

The present invention relates to voice protocols, and more particularlyto protocols such as session initiation protocols.

BACKGROUND

Security systems have traditionally been utilized for detecting unwanteddata. Such unwanted data has included malware, unsolicited messages,etc. However, traditional security systems have generally exhibitedvarious limitations with respect to detecting unwanted data thatutilizes a session initiation protocol (SIP).

For example, voice over Internet Protocol (VoIP) oftentimes employs SIPsfor communicating data. Nonetheless, traditional security systems haveused techniques customarily incapable of detecting unwanted datacommunicated via a SIP. Accordingly, unwanted data has been capable ofbeing communicated via a SIP.

There is thus a need for addressing these and/or other issues associatedwith the prior art.

SUMMARY

A system, method, and computer program product are provided foridentifying unwanted data communicated via a session initiationprotocol. In use, packets associated with an electronic messagecommunicated over a network utilizing a session initiation protocol areidentified. Additionally, it is determined whether the packets includeunwanted data. Furthermore, a reaction is performed, based on thedetermination.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network architecture, in accordance with oneembodiment.

FIG. 2 shows a representative hardware environment that may beassociated with the servers and/or clients of FIG. 1, in accordance withone embodiment.

FIG. 3 shows a method for identifying unwanted data communicated via asession initiation protocol, in accordance with one embodiment.

FIG. 4 shows a system for identifying unwanted data communicated via asession initiation protocol, in accordance with another embodiment.

FIG. 5 shows a method for preventing unwanted data communicated via asession initiation protocol from being communicated to an internalnetwork, in accordance with yet another embodiment.

DETAILED DESCRIPTION

FIG. 1 illustrates a network architecture 100, in accordance with oneembodiment. As shown, a plurality of networks 102 is provided. In thecontext of the present network architecture 100, the networks 102 mayeach take any form including, but not limited to a local area network(LAN), a wireless network, a wide area network (WAN) such as theInternet, peer-to-peer network, etc.

Coupled to the networks 102 are servers 104 which are capable ofcommunicating over the networks 102. Also coupled to the networks 102and the servers 104 is a plurality of clients 106. Such servers 104and/or clients 106 may each include a desktop computer, lap-topcomputer, hand-held computer, mobile phone, personal digital assistant(PDA), peripheral (e.g. printer, etc.), any component of a computer,and/or any other type of logic. In order to facilitate communicationamong the networks 102, at least one gateway 108 is optionally coupledtherebetween.

FIG. 2 shows a representative hardware environment that may beassociated with the servers 104 and/or clients 106 of FIG. 1, inaccordance with one embodiment. Such figure illustrates a typicalhardware configuration of a workstation in accordance with oneembodiment having a central processing unit 210, such as amicroprocessor, and a number of other units interconnected via a systembus 212.

The workstation shown, in FIG. 2 includes a Random Access Memory (RAM)214, Read Only Memory (ROM) 216, an I/O adapter 218 for connectingperipheral devices such as disk storage units 220 to the bus 212, a userinterface adapter 222 for connecting a keyboard 224, a mouse 226, aspeaker 228, a microphone 232, and/or other user interface devices suchas a touch screen (not shown) to the bus 212, communication adapter 234for connecting the workstation to a communication network 235 (e.g., adata processing network) and a display adapter 236 for connecting thebus 212 to a display device 238.

The workstation may have resident thereon any desired operating system.It will be appreciated that an embodiment may also be implemented onplatforms and operating systems other than those mentioned. Oneembodiment may be written using JAVA, C, and/or C++ language, or otherprogramming languages, along with an object oriented programmingmethodology. Object oriented programming (OOP) has become increasinglyused to develop complex applications.

Of course, the various embodiments set forth herein may be implementedutilizing hardware, software, or any desired combination thereof. Forthat matter, any type of logic may be utilized which is capable ofimplementing the various functionality set forth herein.

FIG. 3 shows a method 300 for identifying unwanted data communicated viaa session initiation protocol, in accordance with one embodiment. As anoption, the method 300 may be carried out in the context of thearchitecture and environment of FIGS. 1 and/or 2. Of course, however,the method 300 may be carried out in any desired environment.

As shown in operation 302, packets associated with an electronic messagecommunicated over a network utilizing a session initiation protocol(SIP) are identified. In the context of the present description, thepackets may include any data associated with the electronic message thatis formatted as a packet utilizing a SIP. For example, the packets mayinclude data capable of being constructed into the electronic message.

Additionally, in various embodiments, the electronic message may includean electronic mail (email) message, a voice message, etc. Of course,however, the electronic message may include any message that may becommunicated electronically over the network. It should be noted thatthe network may include any of the networks described above with respectto FIG. 1, for example.

As an option, the electronic message may be associated with a voice overInternet Protocol (VoIP) session. The VoIP session may include anysession in which voice is communicated over the network. For example,the VoIP session may include communication of the packets between atleast two parties.

In one embodiment, the electronic message may include voice communicatedas digital audio. In another embodiment, the electronic message mayinclude a voice message communicated via the VoIP session. To this end,the electronic message may optionally utilize the SIP for beingcommunicated with respect to the VoIP session.

As another option, the VoIP session may use the SIP. Just by way ofexample, a VoIP server via which the VoIP session is initiated may usethe SIP. In one embodiment, the VoIP session may use the SIP forcommunicating the packets over the network.

Further, the SIP may include a protocol for creating, modifying, and/orterminating sessions between at least two parties, in one embodiment.For example, the SIP may be used to create two-party, multiparty, ormulticast sessions. In this way, the SIP may optionally be used forinitiating the VoIP session.

In addition, the SIP may include an application-layer control protocol,a signaling protocol, etc. For example, the SIP may be used for asignaling portion of the session. As another example, the SIP mayoptionally be utilized as a carrier for a session description protocol(SDP) describing media content of the session (e.g. the IP ports to use,the codec being used, etc.). To this end, the packets may utilize theSIP for communicating the electronic message within a session (e.g. theVoIP session, etc.).

As another option, the SIP may be independent of an underlying transportlayer. Accordingly, the SIP may optionally be used on a transmissioncontrol protocol (TCP), user datagram protocol (UDP), stream controltransmission protocol (SCTP), etc. As yet another option, the SIP may betext-based. As still yet another option, the SIP may include apeer-to-peer protocol.

Moreover, the packets associated with the electronic message may beidentified in any desired manner. In one embodiment, the packets may beidentified in response to being received. As an option, the packets maybe received from outside of the network. As another option, the packetsmay be received by a security system device.

As also shown, it is determined whether the packets include unwanteddata. Note operation 304. In the context of the present description, theunwanted data may include any data that is unwanted. Just by way ofexample, the unwanted data may include malware, an unsolicited message,a malicious link (e.g. to a website with malicious content, etc.), etc.

The determination may include comparing the packets to known unwanteddata, in one embodiment. Such known unwanted data may include any datapredetermined to be unwanted. For example, the known unwanted data maybe predetermined by a user to be unwanted. Further, the known unwanteddata may be stored in a database.

In this way, it may optionally be determined that the packets includeunwanted data if it is determined, based on the comparison, that anyportion of the packets match the known unwanted data. Thus, as anoption, it may be determined that the packets include unwanted data ifone of the packets matches the known unwanted data. Of course, it shouldbe noted that it may be determined whether the packets include unwanteddata in any desired manner.

Still yet, as shown in operation 306, a reaction is performed, based onthe determination. The reaction may include any action that may beperformed based on the determination. As an option, the reaction may beselected among a plurality of actions by a user (e.g. via a userinterface, etc.).

In one embodiment, the reaction may include a first action if it isdetermined that the packets do not include unwanted data. The reactionmay include sending the packets to at least one user device (e.g. towhich the packets are destined, etc.). As another option, the reactionmay include allowing the packets to be communicated over an internalnetwork to a destination designated by such packets.

In another embodiment, the reaction may include a second action if it isdetermined that the packets include unwanted data. For example, thereaction may include reporting the unwanted data (e.g. to anadministrator, etc.). As another example, the reaction may includeblocking the unwanted data (e.g. from reaching a user device, such asthe user device to which the packets are destined, from beingcommunicated over an internal network, etc.). As still yet anotherexample, the reaction may include alerting the user device to which thepackets are destined about the unwanted data.

In this way, unwanted data associated with the electronic message thatis communicated over the network utilizing the SIP may be identified.For example, unwanted data associated with a session (e.g. the VoIPsession, etc.) that utilizes the SIP may be identified. In oneembodiment, the unwanted data may be identified in response to adetermination that the packets associated with the electronic messageinclude the unwanted data.

More illustrative information will now be set forth regarding variousoptional architectures and features with which the foregoing techniquemay or may not be implemented, per the desires of the user. It should bestrongly noted that the following information is set forth forillustrative purposes and should not be construed as limiting in anymanner. Any of the following features may be optionally incorporatedwith or without the exclusion of other features described.

FIG. 4 shows a system 400 for identifying unwanted data communicated viaa session initiation protocol, in accordance with another embodiment. Asan option, the system 400 may be implemented in the context of thearchitecture and environment of FIGS. 1-3. Of course, however, thesystem 400 may be implemented in any desired environment. It should alsobe noted that the aforementioned definitions may apply during thepresent description.

As shown, a source device 402 is in communication with a VoIP server 406over an external network 404. In the context of the present embodiment,the source device 402 may include any device capable of utilizing a SIPto communicate packets associated with an electronic message over theexternal network 404. For example, the source device 402 may include anyof the devices described above with respect to FIGS. 1 and/or 2.

To this end, the source device 402 may communicate packets associatedwith the electronic message to the VoIP server 406 over the externalnetwork 404, utilizing the SIP. Such external network 404 may includethe Internet, as an option. Additionally, the VoIP server 406 mayinclude any device capable of providing VoIP services. For example, theVoIP server 406 may facilitate VoIP sessions between at least twoparties. Of course, however, any network server may be utilized withrespect to the VoIP server 406 shown.

In one embodiment, the packets communicated from the source device 402may be routed to the VoIP server 406. In another embodiment, the packetsmay be routed to the VoIP server 406 for being communicated over aninternal network 402 with which the VoIP server 406 is in communication.As an option, a web server, exchange server and/or any other device (notshown) may be coupled to the VoIP server 406.

Further, the VoIP server 406 is in communication with a security systemdevice 408. In the context of the present embodiment, the securitysystem device 408 may include any device capable of determining whetherthe packets include unwanted data, and reacting based on suchdetermination. For example, the security system device 408 may include asecurity server. The security system device 408 may optionally includean intrusion prevention system, an anti-virus system, an anti-spywaresystem, an anti-span system, etc.

To this end, in response to receipt of the packets by the VoIP server406, the VoIP server 406 may forward the packets to the security systemdevice 408. In one embodiment, the VoIP server 406 may forward thepackets to the security system device 408 over the external network 404.Of course, however, the VoIP server 406 may forward the packets to thesecurity system device 408 in any desired manner.

The security system device 408 may accordingly determine whether thepackets include unwanted data. In one embodiment, the security systemdevice 408 may compare the packets to known unwanted data, fordetermining whether the packets include unwanted data. In anotherembodiment, the security system device 408 may scan the packets forunwanted data.

As an option, a script, algorithm, etc. may be utilized for determiningwhether the packets include unwanted data. Just by way of example, ifthe packets match the known unwanted data, it may be determined that thepackets include unwanted data. As an option, the known unwanted data maybe stored in a database located on the security system device 408.

Table 1 illustrates one example of a field of an SIP packet thatincludes unwanted data. For example, the unwanted data may be includedin a field of the packet utilized for indicating the source device 402from which the packet originated, as shown in Table 1. It should benoted that the SIP packet field shown in Table 1 is set forth forillustrative purposes only and thus should not be construed as limitingin any manner.

TABLE 1 “<scriptx=”’<sip:’src=’http://malicious/heap/g.sr’>@192.168.2:5060>; tag=1”

The security system device 408 may further react based on thedetermination of whether the packets include unwanted data. In oneembodiment, the security system device 408 may conditionally send thepackets to a user device 414 (or optionally a plurality of user devices)based on the determination. Just by way of example, the security systemdevice 408 may send the packets to the user device 414 if it isdetermined that the packets do not include unwanted data.

With respect to the present embodiment, the user device 414 may includeany device capable of receiving the packets. For example, the userdevice 414 may include a device designated as a destination of thepackets by the source device 402 from which the packets originated. Inthis way, a device to which the packets are destined may receive thepackets if the packets do not include unwanted data.

As an option, the packets may be sent to the user device 414 via theVoIP server 406. Just by way of example, the security system device 408may send the packets to the VoIP server 406, if it is determined thatthe packets do not include unwanted data. Further, the VoIP server 406may send the packets over the internal network 410 to an internal server412. The internal network 410 may include a LAN, for example. As anotherexample, the internal network 410 may include an enterprise network.

In addition, the internal server 412 may include any server internallylocated with respect to the internal network 410. For example, theinternal server 412 may interface communications received from the VoIPserver 406 at the user device 414. As an option, the internal server 412may include a security system thereon for performing any analysis (e.g.scanning, etc.) with respect to the packets for determining whether thepackets include unwanted data. For example, the internal server 412 mayanalyze packets received utilizing a protocol other than the SIP.

Still yet, the internal server 412 may send the packets to the userdevice 414 (e.g. over the internal network 410, etc.). As anotheroption, the user device 414 may also include a security system thereonfor performing any analysis (e.g. scanning, etc.) with respect to thepackets for determining whether the packets include unwanted data. Forexample, the user device 414 may analyze packets received utilizing aprotocol other than the SIP.

Of course, as another example, the security system device 408 may blockthe packets from being sent to the user device 414, if it is determinedthat the packets include unwanted data. In one embodiment, the securitysystem device 408 may block the packets by quarantining the packets,deleting the packets, etc. Accordingly, a device to which the packetsare destined may be prevented from receiving the packets if the packetsdo not include unwanted data. Additionally, the packets may also beprevented from entering the internal network 410, if it is determinedthat the packets include unwanted data.

As yet another example, the security system device 408 may send analert, if it is determined that the packets include unwanted data. Inone embodiment, the security system device 408 may send the alert to theuser device 414. In another embodiment, the security system device 408may send the alert to a device of an administrator.

The alert may indicate that the electronic message associated with thepackets includes unwanted data, as an option. As another option, thealert may include any information associated with the electronic messageand/or the unwanted data. Further still, the alert may include optionscapable of being selected by a user of the user device 414 forresponding to the electronic message (e.g., such as allowing theelectronic message, blocking future packets from the source device 402,etc.).

While the security system device 408 is described above as reactingbased on the determination of whether the packets include unwanted data,it should be noted that the VoIP server 406 may also be utilized forperforming the reaction. For example, in one embodiment, in response toa determination of whether the packets include unwanted data, thesecurity system device 408 may send an indication of whether the packetsinclude unwanted data to the VoIP server 406. In this way, the VoIPserver 406 may react based on the determination. Of course, as anotheroption, the security system device 408 may send instructions to the VoIPserver 406 indicating a reaction to be performed.

FIG. 5 shows a method 500 for preventing unwanted data communicated viaa session initiation protocol from being communicated to an internalnetwork, in accordance with yet another embodiment. As an option, themethod 500 may be carried out in the context of the architecture andenvironment of FIGS. 1-4. For example, the method 500 may be carried oututilizing the VoIP server 406 of FIG. 4. Of course, however, the method500 may be carried out in any desired environment. Again, it should benoted that the aforementioned definitions may apply during the presentdescription.

As shown in decision 502, it is determined whether packets are received.With respect to the present embodiment, the packets may include anypackets associated with an electronic message. As an option, the packetsmay be received over a network (e.g. an external network, etc.).

If it is determined that packets are not received, the method 500continues to wait for packets to be received. If, however, it isdetermined that packets are received, it is further determined whetherthe packets are communicated utilizing SIP. Note decision 504. Forexample, it may be determined whether the packets are received utilizingthe SIP.

In one embodiment, a format of the packets may be analyzed fordetermining whether the packets are communicated utilizing the SIP. Inanother embodiment, a header of each of the packets may be analyzed fordetermining whether the packets indicate utilization of the SIP. Ofcourse, however, it may be determined whether the packets arecommunicated utilizing the SIP in any desired manner.

If it is determined that the packets are not communicated utilizing theSIP, the packets are allowed to be communicated to an internal network,as shown in operation 506. For example, the packets may be allowed to becommunicated a user device located in the internal network. Such userdevice may include a destination device indicated by the packets. Ofcourse, the packets may optionally be scanned for unwanted data on theuser device, at a device interfacing the user device, and/or any otherdevice within the internal network.

If it is determined that the packets are communicated utilizing the SIP,the packets are routed to a security system device external to theinternal network, for determining whether the packets include unwanteddata. Note operation 508. In one embodiment, the security system devicemay be located in an external network. Thus, packets may be routed tothe security system device over the external network.

In another embodiment, the security system device may include computercode for determining whether the packets include unwanted data. Forexample, the security system device may compare the packets to knownunwanted data, etc. In this way, it may be conditionally determinedwhether the packets include unwanted data, based on whether the packetsare communicated utilizing the SIP.

Moreover, as shown in decision 510, it is determined whether results arereceived from the security system device. With respect to the presentembodiment, the results may include results of the determination made bythe security system device regarding whether the packets includeunwanted data. Thus, the results may indicate whether the packetsinclude unwanted data.

If it is determined that the results have not been received, the method500 continues to wait for the results to be received. In response to adetermination that the results are received, it is further determinedwhether the packets include unwanted data. Note decision 512. In oneembodiment, the determination may be based on the received results. Forexample, an indication within the results of whether the packets includeunwanted data may be identified.

If it is determined that the packets do not include unwanted data, thepackets are allowed to be communicated to the internal network, as shownin operation 506. If however, it is determined that the packets includeunwanted data, the packets are prevented from being communicated to theinternal network. Note operation 514. Just by way of example, thepackets may be blocked, discarded, quarantined, etc. To this end, theinternal network may be protected from entry of packets includingunwanted data that are communicated utilizing the SIP.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

1. A computer program product embodied on a non-transitory computerreadable medium comprising instructions stored thereon to cause one ormore processors to: identify one or more packets associated with anelectronic message communicated over a network utilizing a sessioninitiation protocol; determine the electronic message is associated witha voice over Internet Protocol session; route the one or more packets toa security system device over the network; receive, from the securitysystem device, information indicative of a comparison of the one or morepackets with known unwanted data; determine from the receivedinformation that the one or more packets include unwanted data; andreact in response to the determination that the one or more packetsinclude unwanted data.
 2. The computer program product of claim 1,wherein the voice over Internet Protocol session utilizes the sessioninitiation protocol for communicating the one or more packets over thenetwork.
 3. The computer program product of claim 1, wherein theinstructions to cause one or more processors to identify one or morepackets associated with an electronic message comprise instructions tocause the one or more processors to determine the electronic messagecomprises a voice message.
 4. The computer program product of claim 1,wherein the instructions to cause the one or more processors to identifyone or more packets associated with an electronic message compriseinstructions to cause the one or more processors to determine the one ormore packets are received from outside the network.
 5. The computerprogram product of claim 1, further comprising instructions storedthereon to cause the one or more processors to determine whether the oneor more packets are communicated utilizing the session initiationprotocol.
 6. The computer program product of claim 5, further comprisinginstructions stored thereon to cause the one or more processors tocompare the one or more packets with known unwanted data after it isdetermined that the one or more packets are communicated utilizing thesession initiation protocol.
 7. The computer program product of claim 1,wherein the unwanted data includes malware.
 8. The computer programproduct of claim 1, wherein the unwanted data includes a malicious link.9. The computer program product of claim 1, wherein the instructions tocause the one or more processors to react comprise instructions to causethe one or more processors to report the unwanted data.
 10. The computerprogram product of claim 1, wherein the instructions to cause the one ormore processors to react comprise instructions to cause the one or moreprocessors to block the unwanted data.
 11. The computer program productof claim 1, wherein the instructions to cause the one or more processorsto react comprise instructions to cause the one or more processors toblock the unwanted data from reaching a user device.
 12. A method,comprising: identifying, with a processor, one or more packetsassociated with an electronic message communicated over a networkutilizing a session initiation protocol; determining the electronicmessage is associated with a voice over Internet Protocol session;routing the one or more packets to a security system device over thenetwork; receiving, from the security system device, informationindicative of a comparison of the one or more packets with knownunwanted data; determining from the received information that the one ormore packets include unwanted data; and reacting, with the processor, inresponse to the determination that the one or more packets includeunwanted data.
 13. A system, comprising: a network interface; and one ormore processors communicatively coupled to the network interface,wherein the one or more processors are communicatively coupled to eachother and configured to: identify one or more packets associated with anelectronic message communicated over a network utilizing a sessioninitiation protocol; determine the electronic message is associated witha voice over Internet Protocol session; route, via the networkinterface, the one or more packets to a security system device; receive,from the security system device, information indicative of a comparisonof the one or more packets with known unwanted data; determine from thereceived information that the one or more packets include unwanted data;and react in response to the determination that the one or more packetsinclude unwanted data.
 14. The system of claim 13, wherein the securityserver is configured to send the one or more packets to one or more userdevices over the network after it is determined that the one or morepackets do not include the unwanted data.
 15. The system of claim 13,wherein the system comprises a voice over Internet Protocol server.